How does setting environment variables VPN_SPLITDNS_... help?

pppd gets this envs (same as VPN_ROUTE_*), and setup dnsmasq to handle multi splitsdns situation. (systemd-resolved doest support splitdns in same interface :( )

And this is the other side which collects the envs and pass to network manager:
elsoa-invitech/network-manager-fortisslvpn@master-jammy...splitdns-dev

(that code is still in WIP!)

This doesn't work with plain openfortivpn.

what is not working for you? have you <split-dns ...> settings in your fortissl_xml?

openfortivpn handles DNS internally by default.

openfortivpn handles DNS internally by default.

Sure. if you run openfortivpn in standalone.

With network-manager (gui), ip+routing+dns settings are handled by NM. Thats why ip/dns/routing rules are passed to envvars, and pickup by the linked networkmanager plugin. With this patch splitdns infos are set to env too and nm plugin can/will handle it.

Because this is the repository for the standalone openfortivpn, adding features unrelated to the standalone case is not really an option. Let me try to find some common ground.

My vision for the long term evolution of openfortivpn is as follows:

1. Drop pppd and use embedded PPP code instead.
2. Switch to an external script such as vpnc-script to set up routing and DNS parameters when the tunnel goes up and down. The script will handle IPv6, split DNS, systemd. End-users could write their own script to customize routing and DNS.
3. We could even split openfortivpn into a library and a CLI, with NM using only the library.

Because vpnc-script expects parameters as environment variables, setting up environment variables doesn't sound bad. However, environment variables should be identical to the ones expected by vpnc-script to allow a smooth future transition to vpnc-script. How about having a look at that?